docs(rfc): add stovepipe process step design #308
Open
mnoah1 wants to merge 2 commits into
Open
Conversation
…ditions The existing Request entity deliberately omits timestamps (schema documents "No timestamps: created/updated times are not part of the Request entity"), and nothing in the process algorithm reads them. Align the RFC's Request additions table with that decision.
behinddwalls
reviewed
Jul 7, 2026
Comment on lines
+26
to
+29
| 5. Coalesce: if R.Sequence < Q.latest_request_seq: | ||
| - a newer head exists -> mark R superseded, ack, return. (No slot consumed.) | ||
| 6. R is the latest head. Gate: if Q.in_flight_count >= Q.max_concurrent: | ||
| - park the delivery (extend visibility, no ack/nack, no state change) -> re-check until the slot frees (admit) or a newer head supersedes it. See [Waiting for a slot](#waiting-for-a-slot). |
Collaborator
There was a problem hiding this comment.
do we have to worry about maxAttempt when we increase the visibility timeout or do we need to just do publishAfter semantics in this case? i think when we admit, are we sending for build step right away or waiting for previous run to complete
behinddwalls
reviewed
Jul 7, 2026
| | `name` | Stable logical id (`monorepo/main`); the string ingest accepts | ingest (create) | | ||
| | `last_green_uri` | Bookmark; empty until first green | record | | ||
| | `in_flight_count` | Active Phase 1 validations | process (+1), record/DLQ (−1) | | ||
| | `max_concurrent` | Concurrency cap (default 1) | config at create | |
Collaborator
There was a problem hiding this comment.
do we need this in DB or should this be wire up into the Queue config or some sort of extension?
Contributor
Author
There was a problem hiding this comment.
True, we don't need this here and can have some sort of queue config provider for this type of configuration info.
behinddwalls
reviewed
Jul 7, 2026
| |---|---| | ||
| | `Sequence` | The per-Queue counter value `n` behind the id; the coalescing order key | | ||
| | `BuildStrategy` | `incremental_since_green` \| `full_monorepo`; immutable once set by `process` | | ||
| | `BaselineURI` | Last-green URI used as the incremental baseline; empty for full builds | |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding a more detailed design/implementation plan for MVP version of the
processstep in the overall stovepipe workflow.